Skip to content

Generated SDK #2966549409 (minor) - #214

Merged
reutz19 merged 1 commit into
masterfrom
fireblocks-api-spec/generated/2966549409
Oct 20, 2026
Merged

Generated SDK #2966549409 (minor)#214
reutz19 merged 1 commit into
masterfrom
fireblocks-api-spec/generated/2966549409

Conversation

@sdk-generation-automation

@sdk-generation-automation sdk-generation-automation Bot commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Changelog

2026-10-20

Added

Add Canton calls and offer responses (beta)

Products: Canton (Beta)

Scope: API + SDKs

  • What's new
    Adds beta endpoints to submit a Canton call from a vault account's Canton wallet and to answer incoming Canton offers such as transfers, allocations, and onboarding requests.

  • Impact
    Customers can now submit Canton calls and respond to incoming Canton offers through the API; this is a non-breaking addition and existing integrations are unaffected.

Affected endpoints:

  1. Make a Canton call
  2. Answer an offer

Add public key to proof of address result

Products: Travel Rule

Scope: API + SDKs

  • What's new
    The proof of address result now includes an optional publicKey for the vault key that produced the signature, returned once the proof is signed or completed.

  • Impact
    Customers can retrieve the public key required by Travel Rule counterparties for SUI, TON and XTZ, and existing integrations continue to work unchanged.

Affected endpoints:

  1. Retrieve Trust Network Proof of Address Signature

Add address option to proof of address

Products: Travel Rule

Scope: API + SDKs

  • What's new
    A new optional address field lets you create a proof of address for a non-default derived address on a vault account, supported for UTXO assets only.

  • Impact
    Customers can prove ownership of a specific Bitcoin address instead of only the default vault address, and existing requests continue to work unchanged.

Affected endpoints:

  1. Create Trust Network Proof of Address

Changed

Document mTLS CSR endpoint permissions

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    The webhook mTLS certificate signing request endpoint now documents that it is available only to the Owner, Admin, and Non-Signing Admin roles, matching the other mTLS configuration endpoints.

  • Impact
    Workspace members without one of these roles will not be able to retrieve the mTLS certificate signing request.

Affected endpoints:

  1. Get mTLS CSR

@github-actions

github-actions Bot commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Noted. Expect updates shortly. (Note that this SDK code is auto generated)

@github-actions github-actions Bot added the minor label Oct 20, 2026
@socket-security

socket-security Bot commented Oct 20, 2026

Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Recently published: npm follow-redirects published 3 weeks ago

Location: Package overview

From: package-lock.json → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block

View full report

@semgrep-code-fireblocks

semgrep-code-fireblocks Bot commented Oct 20, 2026

Copy link
Copy Markdown

Semgrep found 6 block-public-registry-refs-in-package-lock findings:

🟠 High severity issue identified in your code:

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/node-releases/-/node-releases-2.0.57.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

@reutz19
reutz19 merged commit 2ca9eb8 into master Oct 20, 2026
29 of 30 checks passed
@reutz19
reutz19 deleted the fireblocks-api-spec/generated/2966549409 branch October 20, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@reutz19